use kind_name as element tag in the xyz file #216
+10
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
superstar54
force-pushed
the
write_kind_name
branch
from
edb0d49 to
684235c
Compare
superstar54
changed the title
yakutovicha
requested changes
May 15, 2024
There was a problem hiding this comment.
Thanks, @superstar54. It looks good. I would only request to modify the _atoms_to_xyz function directly. It is also used inside the trajectory parser, so it makes sense that the change is also present there.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
structure.get_ase()method currently outputs an uncontrollable element tag. For instance, if there is a StructureData with a kind having name =Xand element =Pt, the resulting aiida.coord.xyz file labels this asPt1for theXkind, which can be confusing for users.This pull request modifies the behavior to use kind_name as the element tag in the XYZ file, enhancing clarity and user experience.